Conclusion

 

As more e-business sites seek to retain customers by serving personalized content, they face potential server-side bottlenecks, slow user response time, and increasing infrastructure costs. The WAS dynamic cache service can solve these critical challenges. Caching dynamic content that needs back-end requests or CPU-intensive computations can reduce server-side bottlenecks and maximize system resources, thus boosting performance and reducing infrastructure costs.

The WAS dynamic cache service is easy to use and readily available. You can benefit from using the available comprehensive functions for caching dynamic content. The Servlet/JSP result cache and command result cache make the caching of dynamic content possible - at various levels of granularity for the highest possible cache hits. The replication and invalidation support facilitates caches that can be shared, replicated, and synchronized in multi-tier or multiserver environments. The Edge of Network Caching Support, with its external caches and fragment support, generates a virtual extension of appserver caches into the network.

The WAS dynamic cache service combined with an appropriate external cache, such as WebSphere Edge Server or IBM HTTP Server, can power high volume sites with intensive dynamic content to achieve the highest level of scalability and performance.

The last information in this chapter is a short recapitulation of the caching technologies available for WAS solutions. Refer to Table 14-1.

Table 14-1 Caching techniques

	Middleware	What is cached	Memory or file system
Dynamic Caching	WAS	Results from JSPs Servlets	Both
Fast Response Cache Accelerator1	IBM HTTP Server 2	Results from JSP Servlets	V1.3 - Memory V2.0 - Both3
Web server plug-in	WAS - ESI processor	Results from JSP Servlets	Memory
Caching Proxy	WebSphere Edge Components	Results from JSP Servlets	Both

¹The Fast Response Cache Accelerator is available on Windows NT and Windows 2000 operating systems and the AIX platform. However, support to cache dynamic content is only available on the Windows NT and Windows 2000 operating systems.

²The IHS 2.0 plug-in necessary to support IHS dynamic caching was not available in IBM WAS Network Deployment V5.1 at the time of writing this book.

³IHS 2.0 provides a module called mod_mem_cache, which supports a memory cache and a file desriptor cache.

Despite the fact that we did not focus on static content caching, Table 14-2 provides an overview of static content caching technologies:

Table 14-2 Static caching

	Middleware	Memory or file system
Fast Response Cache Accelerator	IBM HTTP Server	V1.3 - Memory V2.0 - Both
Web server plug-in	WAS - ESI processor	Memory
Caching Proxy	WebSphere Edge Components	Both

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.